Skip to content

Refresh the MobilityDB ecosystem profile: redrawn figure + figure-aligned repository map#10

Open
estebanzimanyi wants to merge 1 commit into
MobilityDB:mainfrom
estebanzimanyi:docs/stream-readiness-findings
Open

Refresh the MobilityDB ecosystem profile: redrawn figure + figure-aligned repository map#10
estebanzimanyi wants to merge 1 commit into
MobilityDB:mainfrom
estebanzimanyi:docs/stream-readiness-findings

Conversation

@estebanzimanyi
Copy link
Copy Markdown
Member

@estebanzimanyi estebanzimanyi commented May 20, 2026

What

Refreshes the MobilityDB organization profile (profile/README.md + profile/images/mobilitydb_ecosystem.svg) — the page visitors see at github.com/MobilityDB — into one self-consistent repository map.

Figure

A redrawn ecosystem diagram:

  • MEOS (the C library) as the broad foundation, with a Portable Data interchange band beneath it — Arrow C Data Interface (in-memory) · TemporalParquet (on-disk) · Temporal Data Lake (storage architecture).
  • Peer surfaces above MEOS — SQL layers (MobilityDB · MobilityDuck · MobilitySpark), Stream layers (MobilityNebula · MobilityKafka · MobilityFlink), HTTP / API (MobilityAPI + the MEOS-API OpenAPI / MCP / runtime contracts), and the six Language Bindings.
  • MEOS-API as a side codegen catalog (IDL JSON + shape catalog) that generates the bindings and the HTTP API contracts.
  • A top layer of application platforms, visualization, and cloud deployment.
  • Every box is colour-coded; its colour matches the marker on the corresponding README section. One inner box per component, uniform 16px borders, one title font, one content font.

Repository map (text)

Each section mirrors a figure box (its heading marker = the box colour) and lists components as bullets, each linking to its repository plus the underlying tool / RFC / standard. Covers the BerlinMOD parity contract (SQL and streaming), the TemporalParquet (#870) and Temporal Data Lake (#913) RFCs, the mest indexing submodules, datasets, packaging, research, and the archived-repository successors.

Review

Documentation only — no code changes.

@estebanzimanyi estebanzimanyi force-pushed the docs/stream-readiness-findings branch 4 times, most recently from c4e9bfa to dbb22e5 Compare May 21, 2026 06:17
@estebanzimanyi estebanzimanyi changed the title docs(profile): describe stream-layers parity contract and bindings split docs(profile): describe stream-layers tier as a solid peer (figure + text + in-flight PRs) May 21, 2026
@estebanzimanyi estebanzimanyi force-pushed the docs/stream-readiness-findings branch 3 times, most recently from 5c06ad0 to 66221e2 Compare May 22, 2026 17:02
@estebanzimanyi estebanzimanyi changed the title docs(profile): describe stream-layers tier as a solid peer (figure + text + in-flight PRs) docs(profile): the MobilityDB ecosystem — four peer tiers, Temporal Data Lake, MEOS-API binding source May 22, 2026
@estebanzimanyi estebanzimanyi force-pushed the docs/stream-readiness-findings branch 18 times, most recently from 8a72373 to fe2f598 Compare May 23, 2026 07:06
@estebanzimanyi estebanzimanyi force-pushed the docs/stream-readiness-findings branch 13 times, most recently from 761a01f to 0900d4f Compare May 23, 2026 09:49
Redraws the ecosystem figure — colour-coded layers (each matching its README section marker), one inner box per component, MEOS as the broad foundation, MEOS-API as a side codegen catalog feeding the language bindings and the HTTP API contracts, and a portable-data interchange band beneath MEOS — and rewrites the repository map so every section mirrors a figure box and lists its components as bullets linked to their repositories, underlying tools, RFCs and standards.
@estebanzimanyi estebanzimanyi force-pushed the docs/stream-readiness-findings branch from 0900d4f to 6e2054b Compare May 23, 2026 09:54
@estebanzimanyi estebanzimanyi changed the title docs(profile): the MobilityDB ecosystem — four peer tiers, Temporal Data Lake, MEOS-API binding source Refresh the MobilityDB ecosystem profile: redrawn figure + figure-aligned repository map May 23, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant